Confused betwen user cases and user stories

Hello,
I am wondering if you can sort out my confusion concerning user
stories and use cases:
1. When is appropriate to develop user stories, instead of use cases?
2. When is appropriate to develop use cases, instead of user stories?
3. Can one capture the business requirements [stakeholder requests] as
user stories, as part of the process of elaborating the business
problem domain, and then define the solution requirements with use
cases? Or for the first iteration, capture user stories, and for the
second, more detailed iteration, define use cases from the user
stories?
3. Can one develop UML models from user stories?
4. How do user stories fit into an RUP framework?
5. When one is capturing user stories, should one also define the
acceptance test for that user story at the same time?
6. What are the limitations for user stories?
7. How does user stories work with requirements management tools such
as Rational RequisitePro: do you need to define special requirement
types and attributes for them?

Best Regards,

Mike Little

.