Yes and no.  There is some code that tries to account for an esoteric error that's internal to ADO.NET and which typically only occurs in high volume situations.  But it seems that while I reduced the frequency of this issue for some, others have occasionally continued to run into this.  My only repros of this occurred without the mapper involved also, which is how I determined it was an internal ADO.NET error, and some customers I worked with concluded the same thing.  But since it has since raised its head again, and some have now said that this does not occur without the mapper, I can no longer make a promise that its fixed in every case.  But it is fixed for every case that I have been able to repro, and I have not seen this occur in my own applications.

Thanks, Paul Wilson