MVC versus MVP for a WinForms app

Both in MVC and MVP the presentation layer consists of view objects, and application logic consists of controller\presenter objects. For each view object a corresponding controller\presenter exists and vice versa. And although MVC and MVP are based on a common 3-tier principle: views process only presentation needs and controllers\presenters handle application logic, these patterns have two major differences:

1. In MVC controllers receive and process user input, but in MVP views receive user input and then merely delegate processing to the corresponding presenters. That is why MVP pattern better fits modern UI environments (Windows/Web forms) where view classes themselves handle user gestures.
2. In MVC controllers affect their views by changing the intermediate presentation model, which the views are subscribed to (by observer pattern). This makes views pure observers without direct access to them. MVP on the other hand violates this "pure observer" rule by providing a direct link from a presenter to its view. This makes MVP more handy as compared to MVC.