I've adopted the Win API Clipboard work-around to the bug in the VB clipboard but after doing so realize that it's not really covering what I need.
What I really need is a way to detect if the user manually initiated a range copy [CTRL+C] prior to starting the macro procedure. Excel gives us the marching ants around the copied cell which is also the Active cell but so far I'm unable to discern any distinction in the cells Border properties indicating marching ants or otherwise.
A test of the WIN API clipboard might be helpful as a secondary workaround but detecting an active Excel copy-in-progress is preferred.