The optimization of starting initialRNGByte at status requires us to change the inner loop to assume initialRNGByte is the first value checked rather than the value before that. We can do so without loss of generality.
We also need to check the case of currentRNGByte < status after rerolls.
Resolves #3.
There were two issues at play:
initialRNGByteatstatusrequires us to change the inner loop to assumeinitialRNGByteis the first value checked rather than the value before that. We can do so without loss of generality.currentRNGByte < statusafter rerolls.