Note: on Windows, this code does not yet use the native Cryptographic API as a source of random numbers (it uses the system clock instead). As a result, the sequences it generates may not be highly independent.
P.S. I'm not affected by this bug.
For security's sake, it would be nice for MWC to actually use the Windows crypto API.
For CLI cleanliness, it would be nice just to get rid of those warnings.