Child mouse events also fire on ancestor controls

Mouse events raised by a child control also fire on ancestor Objo controls. For example, clicking a Canvas inside a ContainerControl invokes both the Canvas MouseDown handler and the ContainerControl MouseDown handler. The ancestor should receive mouse events from its own surface, not from a nested Objo control. The current behaviour can run multiple handlers for one pointer action and makes reusable nested controls unpredictable.