Added Capstone Engine PowerShell binding

Consider this to be an alpha release until the C# binding is published.
Major update to Capstone disassembly module

* Refactor of C# capstone binding
* Now compatible in 32 and 64-bit PowerShell
Adding 64-bit lib file
Fixes #23 - $Password was not being cleared
Updated C# Capstone binding to latest version
Updated usage documentation
Bug fixes for Invoke-TokenManipulation

Processes could not be started when the script was being run from
Session 0. The fix is to use the CreateProcessAsUserW function when
running in Session 0. This API requires SeAssignPrimaryTokenPrivilege
priviege, so for non-session0 calls I still use CreateProcessWithTokenW
which does not require special privileges.
Merge pull request #25 from clymb3r/master

Bug fixes for Invoke-TokenManipulation
Capstone module now incorporates framework 2.0RC1

* I also moved the contents of Get-CSDisassembly.ps1 into Capstone.psm1
Capstone.dll returns the correct number of operands now.
Disable non-standard cmdlet verb checking
Upgraded Capstone framework libs to 2.0

These are the compiled libs straight from
http://www.capstone-engine.org/download.html
Generate a non-terminating error if there's a binding/framework version mismatch

The user should at least be made aware if they're using an unsupported
framework library version.
Update Invoke-ReverseDnsLookup.ps1

Added pipeline support and verbose statement.
Merge pull request #26 from obscuresec/master

Update Invoke-ReverseDnsLookup.ps1
Removed mimikatz.

This doesn't need to reside in PowerSploit. Those that are truly
paranoid should validate that the embedded executable in
Invoke-Mimikatz.ps1 is indeed mimikatz.

This was causing AV to flag upon downloading PowerSploit.
Add Get-Entropy
Inject-LogonCredentials has been renamed to Invoke-CredentialInjection.

Added a check to ensure the script isn't being run from Session0 with
the "NewWinLogon" flag. This flag does not work in Session0 because
winlogon.exe tries to load stuff from user32.dll which requires a
desktop is present. This is not possible in Session0 because there is no
desktop/GUI, so it causes winlogon to load and then immediately close
with error code c0000142 indicating a DLL failed to initialize. There is
no way to fix this that I know of, if you need to run the script from
Session0 use the "ExistingWinLogon" flag.
Merge pull request #28 from clymb3r/master

Inject-LogonCredentials has been renamed to Invoke-CredentialInjection.
Changed Inject-LogonCredentials name to Invoke-CredentialInjection