Jim Showalter - 2009-09-09

You can close this one--it's due to there not being a default constructor, so the VM creates one, which of course isn't covered. Adding a private default constructor and invoking it via reflection in the unit test makes this problem go away.