I really appreciate the simplification of using this instead of full PEX. Great effort.
One think, I noticed that you need to add an exception or assert in the code under test.
My feeling is that developer will never do that, and hence digger will not show the potential bug.
So the question is, is code digger meant to be used on a parameterized unit test rather than the actual code? Or the required additions are the appropriate way to write good code? and perhaps Code Digger should say it and refrain from creating the table.