Use simpler pip bootstrap

Hopefully fixes #564

It has something to do with Windows paths, and maybe quadruple backslashes, but this fix works without quadruple backslashes, so I like it infinitely better.

Problem found on [at least] Python 3.3.4, x64, Windows 8.1.

Problem encountered:
```
C:\Users\Ivo>virtualenv testfoo
Using base prefix 'C:\\Python33'
New python executable in testfoo\Scripts\python.exe
Installing setuptools, pip...
  Complete output from command C:\Users\Ivo\testfoo\Scripts\python.exe -c "import sys, pip; sys...d\"] + sys.argv[1:]))" setuptools pip:
  Traceback (most recent call last):
  File "<string>", line 1, in <module>
AttributeError: 'module' object has no attribute 'main'
----------------------------------------
...Installing setuptools, pip...done.
Traceback (most recent call last):
  File "C:\Python33\lib\runpy.py", line 160, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "C:\Python33\lib\runpy.py", line 73, in _run_code
    exec(code, run_globals)
  File "C:\Python33\Scripts\virtualenv.exe\__main__.py", line 9, in <module>
  File "C:\Python33\lib\site-packages\virtualenv.py", line 824, in main
    symlink=options.symlink)
  File "C:\Python33\lib\site-packages\virtualenv.py", line 992, in create_environment
    install_wheel(to_install, py_executable, search_dirs)
  File "C:\Python33\lib\site-packages\virtualenv.py", line 960, in install_wheel
    'PIP_NO_INDEX': '1'
  File "C:\Python33\lib\site-packages\virtualenv.py", line 902, in call_subprocess
    % (cmd_desc, proc.returncode))
OSError: Command C:\Users\Ivo\testfoo\Scripts\python.exe -c "import sys, pip; sys...d\"] + sys.argv[1:]))" setuptools pip failed with error code 1
```
Also seems to be present on Windows Server 2008 3.3.4 as indicated by that issue.

I am on Windows ATM so checking it works on both *nixes should be in order before a merge.