Yeah, Microsoft absolutely should've made their containers use throwing move-constructors in violation of the standard, in order to better adhere to the standar

Yeah, Microsoft absolutely should've made their containers use throwing move-constructors in violation of the standard, in order to better adhere to the standard. In reality, it's a defect in the standard, plus a quality-of-implementation issue in the Microsoft's C++ Standard Library.