Its funny to see this new technical note posted by the SQLCAT team today because we just recently had a discussion about this on Twitter. My good friend Sankar Reddy (Blog/Twitter) sent me an IM with the link to this page based on the twitter discussions.
Essentially, the problem deals with inserts into a table with a identity column as the primary key and clustered index key. Under a busy enough workload all inserts occur on the same page at the end of the B-Tree and the processes wait on the Page Latch to be released on the page. In this technical note, the SQLCAT team covers how to deal with this scenario using Partitioning and hashing.