Why do scaled and masked captivate swfs respond to clicks outside the mask? Can it be stopped?

Even if anyone just has any knowledge of how Captivate 3 movies actually monitor the mouse, I'd be happy to hear it. In other words, can anyone confirm my hunch? If we knew the internal structure of the Captivate SWF would it be possible to clear and restore some function as the mouse moves inside or outside of the target area? Something like this:

on mousemove {

     if mouse has crossed boundary to the outside {

          functionBuffer = container.whatever.whatever.function;

          container.whatever.whatever.function = null;

     }

     else if mouse has cross boundary to the inside {

          container.whatever.whatever.function = functionBuffer;

     }

}

This would kill Captivate's mouse functions and then bring them back to life, as the mouse exits and re-enters the masked Captivate area. Two questions:

1. If we knew the necessary whatever.whatever.function information, would this work?

2. Does anybody know the necessary whatever.whatever.function information?

Philip at Pipwerks already suggested placing a movieclip with button behavior in front, in order to block the mouse from Captivate, but that does not work. The outer bordered region in the demo file above already has just such a movieclip, and the counter at the top-right corner counts the clicks. So you'll see that when the Captivate movie is scaled, whether it's masked or not, both that region and the Captivate respond.