How do you know what addresses were not parsed on import or after running script

After selecting the checkbox to Parse Addresses, after importing (as well as after running the parsing script on existing records), there is currently no way to find the contacts whose addresses did not get parse so that a user can then manually parse the addresses. When addresses do not get parsed during import of after running the script, all we get is a message saying how many addresses weren't parsed. The only other way you can find out what wasn't parsed is if you happen by chance to be on a particular record and you edit the address element and then you can fix it there.

This could become problematic for creating walk lists (in CiviEngage) because the walk lists will not be generated properly.

Could there be some mechanism for the user to find contacts whose addresses were not parsed, so that s/he can do the manual parsing?

In addition, after some testing and playing, we noticed that CiviCRM has issues parsing addresses that have "FLO" in the street name. Here are examples of what couldn't be parsed:

• 3310 FLO LN
• 3310 FLO AVE
• 3310 FLO LOR LN

But addresses like "3310 CIR LN" have no problem being parsed.
Is there something in the parsing logic that's causing this?

We tested and have been able to recreate the problem on the civicrm 3.1 demo site as well as our 3.1 test sites.