Fix issue finding volumes if running vagrant destroy after server is destroyed
Use same check as connect.rb for Vagrantfile disks section
Fix to prevent stack trace failing to find VM, if destroying a non-existant VM
Update README for more volume related material
Retry server deletes until we are sure the VM is dead -- only then remove IP's and volumes
Merge pull request #95 from cbaenziger/volume_support

thx a lot! Fix for #92 and #94
Merge pull request #97 from cbaenziger/issue_96_fix

thx for updating the REAME and fixing the issue! Continuously destroy VM until it goes away
version bump to 0.11.0
Fix conflict with latest version of head