A special thanks goes to WoodyZ and Darius for taking the time to respond. It is so reassuring when a vendor confirms and acknowledges a bug. All too often such reports disappear into a black hole. Hopefully we will see the fix in the next dot-release (and hopefully VMware has tested their other settings to make sure the fault is unique to the Memory setting).
Certainly the workaround is easy enough.