Multiple group audience + Views = multiple results

I'm pretty sure it's og_access' fault, though it might be faulty Views for all I know.
It also might be a double-post (due to the nature of the beast) but I haven't found any reports about this.

Prequisites:
- a node is assigned to multiple groups
- a user is a member of multiple groups and is not admin (in any context)
- those two sets of groups have a conjunction of size larger than 1 (ie: the user is a member of more than one groups that the node is assigned to)

Real example:
The node is assigned to groups 388 and 367, the user is assigned to groups 402,388,367,387. The below WHERE clause is produced:

[...]
FROM
       (SELECT DISTINCT ON (nid) * FROM node) node 
[...]
	INNER JOIN node_access na ON na.nid = node.nid 
WHERE 
	(
      (
	na.grant_view >= 1 
	AND (
		(na.gid = 0 AND na.realm = 'all') 
		OR (na.gid = 0 AND na.realm = 'og_public') 
		OR (na.gid = 402 AND na.realm = 'og_subscriber') 
		OR (na.gid = 388 AND na.realm = 'og_subscriber') 
		OR (na.gid = 367 AND na.realm = 'og_subscriber') 
		OR (na.gid = 387 AND na.realm = 'og_subscriber')
	))
[...]

When that happens the inner join on "na" causes the whole query to produce multiple results for a particular node. That in conjunction with not selecting any group information for a node in the query will create identical result rows, which in most cases is unwanted (my case in particular).

This will cause multiply display ANYWHERE the node should apper when using views for non-admin users.

Temporary solution:
Hacked the Views code to make a "distinct" filter on all query results.

Real solution:
None imaginable.