Probably a question for MS to be honest with you. I could easily see it being in R2 if they cut off that branch of development with the original bug in it. And considering that it applies to late SP1 on non-R2 edition I would say the probability is high that R2 contains the bug too. But just a supposition on my part.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service