I agree, it is a good reason.  Maybe there is a middle-ground, less horrible for finding unknown  bugs, and also predictable & repeatible.  How about using a deterministic PRNG and using the ``iterations`` feature.  Run each iteration from it's index into a ``seeds_csv`` option?  Maybe if there's no seed value, pick a random-seed, display it prominently for each iteration.  This approach would get us the predictable and repeatable component, and let  the  coverage expand to as wide as the number of seeds provided and/or ``iterations`` specified.