Memory consistency model

Memory consistency has a central position in assuring the programmer that his program executes as expected. Currently, two views which memory model transactions should target are expressed. On one hand there is the approach targeting an enhanced weak-isolation memory model. Transactions are expected to behave like locks and the STM enforces an ordering of transactions [here]. On the other hand a strong isolation memory model is proposed. In addition STM mechanisms to change the commit order are favoured [here].
Although strong isolation grants composability, we do not consider it to be practical in an unmanaged environment.
Further, the upcoming C++ standard will not consider strong isolation:
From the Abstract: "We give no semantics to programs with data races. There are no benign data races in C++."
We share this view of treating racy programs and want transactions to behave accordingly in an unmanaged environment.
We hope to see a lively discussion on the pro's and con's of memory models.