I'll take the challenge.
I asked about this on github a while back, it looks like it could be a real gamechanger in terms of scanning speed for the client.
This is a quote from Gavin Andresen in his blog post talking about increasing the block size of Bitcoin:
Of course, we won't be running current code on tomorrow's hardware; we'll be running better code. CPU usage should go down by a factor of about eight in the next release when we switch to Pieter's libsecp256k1 library for validating transactions.