Performance: Small bug in MySemaphore.WaitSeconds may lead to unnecessary cpu utilization on windows

I was wondering, why following code using cpp.vm.Lock was leading to
100% cpu utilization of a single core on windows:
https://gist.github.com/ZuBsPaCe/3ab1302f981be2ea4c55

The reason was simple: Method MySemaphore.WaitSeconds in Thread.h uses
WaitForSingleObject of the windows api, which expects milliseconds. But
currently the inSeconds parameter gets divided by 0.001 instead of
multiplied with 1000.0.

Only windows builds seem to be affected.

WaitForSingleObject:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms687032(v=vs.85).aspx
WaitForSingleObjectEx:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms687036(v=vs.85).aspx
Merge pull request #105 from ZuBsPaCe/bad-performance-mysemaphore-wait

Bug in MySemaphore.WaitSeconds leads to 100% cpu on windows.
Nice one - back to primary school for me.  At least I called the variable "seconds" so the fix is easy to verify.