title: Is there a slim reader/writer lock for .NET 2.0?
body: <p>I've looked at the ReaderWriterLock in .NET 2.0 and the ReaderWriterLockSlim in .NET 3.5, and the slim version doesn't use kernel objects for the locking. For my context, which can potentially generate a large (but not huge) amount of objects, this sounds better.</p>
  
  <p>But the code I write needs to be used in both .NET 2.0 and 3.5 during a transition period, so the 3.5 version, while looking good for my purposes, can't be used.</p>
  
  <p>Does anyone have, or know of, a similar class that I can plug into .NET 2.0 and get some of the same benefits with?</p>