I have updated the code in 2.1.1 to avoid this problem. The oddly termed exception is actually coming from the Microsoft system library. It must be a bug there. Anyway, thanks to your help, users of this library should never encounter it again.
↧