Document and consider the possibility of enforcing in the code the concurrency policy to access/change the OFCV associated with an OperationContext.

The rule should be: only the thread that owns the OperationContext should set the VersionContext, if follows that it's the only thread that can read from it without holding the client lock. All other accesses (write from the thread owning the OperationContext or read/write from other threads) must be synchronized.