Reimplement toBytes to avoid Charset.encode method which may leak hashes

Reimplement the parsing to avoid the regex group method which creates strings that we can't sanitise.

Switch to cleaner log2 implementation

Switch to more modern and stronger RNG

Fix potential timing attack due to manually comparing hashes with a loop ...

The number of loop iterations can be used as an indication of how close a guessed hash is to the correct one.

Overwrite byte arrays in check method

Updated deps, upped work factor, add timing tests

log2 now complains if it is given a number that is not a power of 2.

Minor edit.

Added example and README.

Switched to CharSequence/CharBuffer.

Initial commit.