Under certain race conditions, the remove loads old version from cache and invalidates this version, but the remove fails because newer version was inserted in the meantime. This affects cached collections as these are only invalidated, the version is not incremented in cache and therefore a DB read may try to putFromLoad newer version concurrently with another invalidation.

Since the SPI does not provide the proper version (and lockItem call for collections does not use version either), the solution has to fallback to timestamp-based comparison.