I have found (in SQL 2000) when I go to delete logins that if they own jobs or SPs/UDFs/Views, SQL asks me if I want to reassign the objects and offers me a list of still valid logins I can choose from to assign the objects to.
In 2005, this process is simplified because now all objects belong to a schema and when you delete a login, unless it owns a schema, you don't have to worry about the objects and their permissions because they will apply across the board. BTW, in my experience, 2k5 doesn't allow deletion of a login which owns a schema. You have to delete all the objects owned by the schema (or reassign them) and then delete (or reassign) the schema before you can delete the user who owns it.
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"