Definitely a handy script. Although the developers in my company all have dbo privileges to the development database, our Windows Group login is mapped to a user other than dbo. We are forever creating procedures without specifying the [dbo]. in [dbo].[<procedurename>] and ending up owning the procedure instead of dbo.
I would make one enhancement to the script. Right after the SET NOCOUNT ON line, I would add this line:
DELETE FROM [ObjList]
to prevent duplicates from a previous execution from appearing in the table