Microsoft quietly released another cumulative update for SQL Server 2005 Service Pack 3 this week. So quietly, in fact, that it took me 5 days to notice. As Chad Miller noted in his comment, this is the first build of SQL Server 2005 that supports the "lock pages in memory" setting on Standard Edition. You can read about the release here:
http://blogs.msdn.com/sqlreleaseservices/archive/2009/06/15/cumulative-update-4-for-sql-server-2005-service-pack-3.aspx
If you are still running on SP2, you should consider testing and deploying SP3. If that is not in the cards, then you will also want to look at CU #14 for SP2, also released on Monday:
http://blogs.msdn.com/sqlreleaseservices/archive/2009/06/15/cumulative-update-14-for-sql-server-2005-service-pack-2.aspx
Why do I think you should be on SP3 and not SP2? Well, from the fix lists for the two branches, it is clear that more fixes are going into the SP3 branch (20 fixes, vs. 6 fixes on the SP2 side). However, as with previous "parallel" CU development, the SP3 branch fixes are not a superset of the SP2 branch fixes. Observe that only 2 fixes are common to both, 4 are in CU14 for SP2 only, and 18 are in CU4 for SP3 only: