Incorrect number of rows returned by pager for search results when a search result profile is used

This is related to NYSS issue: http://senatedev.senate.state.ny.us/issues/show/3629

However, the actual issue is described most clearly in the last comments.

I replicated the bug on my local 3.3. install with sample data using these steps:

• search for 's' - returns 82 contacts with 50 rows on page 1
• updated several contacts in the resultset to have different location types for their email, phone and address
• repeated search for 's' , and first page has 50 rows
• created a profile for search results matching this one profile on their dev machine: http://sd99.crmdev.nysenate.gov/civicrm/admin/uf/group/field?reset=1&action=browse&gid=11
• modified Global Search Settings to use that profile
• repeated search for 's' , and first page now has 48 rows (although pager says "Contacts 1-50") so this is a bug (at least in 3.3 - but probably in 3.4) which seems to be triggered by a combination of search results profile (probably related to the used of "primary" address, phone and or email profile fields) and contacts with varied location types for these elements.