You can throw this into a looping stored procedure and either stick it in a table or export it to a spreadsheet. This code is good for SOX compliance (making sure who has what permissions) and if run on a weekly or daily basis, helps you track down security abusers who have added permissions to people that shouldn't have them.
Any information stored should be kept in a DBA team administrative database or a restricted file share, though, so no developers or users can access the info and use it to cause trouble.
My apologies for not being able to post the whole SP, but I don't own the whole code (just the bits I fixed up) and I don't have permission to post everything publically. If you have any questions, just let me know.