added invoke-portscan module
removed a few comments
fixing powershell 2.0 compat
Powershell 2.0 fixes - should work now
small style update
Addressed mattifestation feedback

See https://github.com/mattifestation/PowerSploit/pull/6#issuecomment-19289063

1) I like this feedback a lot and took it.

2) I tried going thread only but it got messed up with very large scans. Eventually,
I didn't think it was worth the amount of effort to make it reliable with only threads

3) Tried to do this

4) Did this

5) I like the idea in general and I took this one place (top-ports), but not for the two
examples you gave. The reasoning is, I want people to be able to specify various options
and arrays aren't that flexible. For example, I want people to specify a port list like
"80,90,8080-8090". Similar with CIDR, since that's one option, but they could also be
specifying hostnames e.g. "google.com,192.168.1.1/24,10.0.0.1"
fixing EOL spaces
fixing EOL spaces (again, sorry)
IPv6 support in hosts param
Merge branch 'Portscan' of https://github.com/webstersprodigy/PowerSploit into webstersprodigy-Portscan

Conflicts:
	Recon/Recon.psd1
Added Invoke-Portscan to README
Merge pull request #10 from mattifestation/webstersprodigy-Portscan

Webstersprodigy portscan