1. Get my hosting provider to allocate additional IP's to the host computer that I'm renting. Don't assume this is done even if the server 'includes 4 IP addresses' or whatever. This sometimes means they won't charge you but you still have to ask. This seems to be especially true in Europe. It avoids needless IP waste.
2. One IP will be for the host, the other for the VMs. So, you must use bridging as your network choice on the VM. Use an IP given to you by the hosting company, and copy the rest of the details from the host computer (dns, gateway). AFAIK, bridging is the only way to do this.
3. Your VM will then appear like a real machine on the Internet.
4. Chances are this will work. BUT...
Some providers (Hetzner for one) stop multiple mach adressses being used on the same physical port IIRC. There is a workaround I believe.
Windows Web Server 2008 R2 is not a supported host O/S for VMWare server (but it is a supported guest O/S). You may find it works however.
About what version of VMware are you talking about?
The best performance you would get from ESXi, however this is the 'OS' and by installing a tool on a client you can add/configure VM's.
Bridging of the network interface is automatically done by ESXi, so no work there.
If you want to have as base Windows, you can use VMware Server.
I think you can easily configure when creating a VM, you want to bridge the connection. However I'm not 100% sure of this.
On Windows 2008 R2 Web Edition, Hyper-V is not supported (unfortunately).
VMware 7 is considered a desktop application, rather not use that for production servers (however, the same counts for VMware Server in my opinion).
You could consider Microsoft Virtual Server, although I'm not 100% convinced it works on Web Edition.