So, found a pretty obscure bug today.
Popularity Contest's `get_current_posts()` method was altering the global $wpdb object's `current_queried_object` reference.

When pop-contest would call `$wpdb->get_posts()` it was causing the global object to re-query and in some circumstances it was causing the object to return a different set of posts. We found this when the edit link in the admin-bar for any post who was an child page named 'about' was wrong. The admin-bar calls `get_queried_object()` which looks at an internal pointer on the global `$wpdb` object to see who was queried. After pop-contest pulled the current posts the queried object's id was different.

I tracked it down to this and found the attached patch to work. Instead of calling `$wpdb->get_posts()` the patch just loops over the global `$wpdb` object's existing $posts array. 

Stack trace was:

akpc_content_pop()->
	get_post_rank()->
	get_post_total()->
	get_current_posts()