jim.gill wrote: Woody -- Your message is complex, please forgive me if I misunderstand.
Come on Jim, it's not that complex! 
Once you get a hybrid MBR onto your system, it will probably stay around through your rebuilds unless you are particularly aggressive about erasing disks and repartitioning. That's probably what's occurring in your case, though this is speculation on my part.
I strongly doubt that anything was left over from previous installs as I alway zero out the whole disk using 3rd party tools in addition to running the HDD Manufacture specific diagnostic tools as well to make sue the disk is 100% okay and have to reestablish the EFI and HFS+ partitions. If by following the basic Boot Camp install directions which explicitly and specifically state to reformat to NTFS and not delete/recreate the partition Windows is being installed to the action updates the Protective MBR that certainly makes sense as why VMware Fusion had no problems recognizing the Boot Camp partition even though I didn't allow it to be run virtually. This must then have to do with explicitly and specifically how resonanttoe preformed all relevant steps.
I've see it where a User would delete/recreate the partition during the install and the Protective MBR was defiantly not updated and a manual update would be required. There is a VMware Employee, mudaltsov, that posted directions on how to sync the GPT/Protective MBR in cases such as/similar to this.