No - I removed it in SQL Server 2005 because people were causing problems for themselves. See http://www.sqlskills.com/blogs/paul/dbcc-pintable/ for some explanation.

If you find a table is dropping out of cache, even though heavily used, because other tables are also heavily used and they can't all be kept in memory, put in a SQL Agent job that does a SELECT COUNT (*) with an index hint to force index ID 1. Adjust periodicity as necessary.

Cheers