Cisco PIX - NAT - Multiple IP addresses/ports to one port

OK, perhaps my initial question wasn't totally clear...
Where you see '10.0.0.<x>', think of an address in the public ip space - perhaps not the best choice of example
IP numbers... - this system is not using any private ip space.

Normally, a host is made visible on the external interface of the PIX by a
static (inside,outside) Host1 Host1 netmask 255.255.255.255 0 0
command.

What I want to accomplish is to have requests which come in on the external interface for Host1:443, Host2:443 and
Host4:443 get rewritten to Host4:8443.
I don't want to wildcard it though (if such a thing is even possible), since requests on Host3:443 should go straight
through to Host3:443.

I suspect I'm still being as clear as mud here...let me know if I need to clarify things again.

That makes sense, but despite my initial confusion, my original statement holds true.  The PIX is not a load balancer.  You cannot statically map multiple external ports to a singe IP and port.  Mapping is a one to one relationship.  

Let me add this.  Normally you would not map an internal address to itself like you are suggesting.

Rather than: static (inside,outside) Host1 Host1 netmask 255.255.255.255 0 0

It should be: static (inside,outside) Host1_External Host1_Internal netmask 255.255.255.255 0 0

Also, I'm not certain why you would want multiple IP's on the outside to a single IP on the inside.  That's highly rare.  Can't you direct people to a single published IP?  Why the need for multiple public IP's for a single resource?  If this is for SSL, usually the internal server would also have multiple IP addresses, so you would still have a 1 to 1 relationship.

Well, the mapping is the way it is, because that's the way our hosting company set things up...I'm agree
that it's a bit strange but, since I can blame someone else for that, I will :)

As far as why we're doing this, we're basically migrating some customers who are on multiple different
servers to one server. We have other solutions we can use - this was just the easiest one. Anyway, you've
saved me loads of time trying to find a solution that doesn't exist, so thanks.

One final thing...our config currently has:
access-list ACL-IN permit tcp any host Host2 range 40000 41000

If I wanted to map those connections to a different host, would I need 10000 lines of the form
static (inside,outside) tcp Host2 40000 Host4 40000 netmask 255.255.255.255 0 0
static (inside,outside) tcp Host2 40001 Host4 40001 netmask 255.255.255.255 0 0

or is there some sort of range command I could use to do this instead?