Rev. 80: Error with counter and analytic privilege

Question

Hey guys,
I have the following structure in my model:
Attribute View (AT) --> Calculation View 1 (CV1) --> Calculation View 2 (CV2)
The calculation views only contain the default aggregation. Additionally CV1 has a counter on one of the columns.
The content is about analyzing roles from ERP.
AT has columns RIAExtractID (its a GUID), AGR_NAME (Name of the composite role), CHILD_AGR (Name of the single role).
CV1 has the same columns but also a counter on CHILD_AGR called "NumberofAssignedSingleRoles".
CV2 has all columns of CV1 but not CHILD_AGR.
Here is how it looked like in Rev72: (filtered for one AGR_NAME = AC280-RECHERCHE-REPORTS)
AT:
CV1:
CV2:
(I would not need CV2 to get this result (I could just select these 3 columns from CV1). However, in CV2 the Column NumberofAssignedSingleRoles is of type "attribute" whereas in CV1 it's a "measure", and with this "hardcoded" aggregation in CV2 I can then apply a filter on NumberofAssignedSingleRoles in an OData request giving me for example all roles which have less than 5 single roles assigned. Otherwise you can't filter on a measure.)
However, now with Rev. 80 the result of CV2 looks like this:
Although, AT and CV1 still look the same (and return 4 rows with each a different CHILD_AGR). No matter how many child roles have been in CV1, CV2 gives me NumberofAssignedSingleRoles = 1 for every AGR_NAME!
Trying to track the issue down, I found that using SYSTEM user gives me correct output of NumberofAssignedSingleRoles = 4.
Since one major difference between my user for testing and SYSTEM are analytic privileges.
Currently there is a restriction in the analytic privilege for AT: RIAExtractID = 001CC4F....
When I remove this restriction, the output is correct, too. (i.e. 4 rows in AT, 4 rows in CV1, Counter= 4 in CV2)
When I add the restriction again, the output is wrong. (i.e. 4 rows in AT, 4 rows in CV1, Counter = 1 in CV2)
I'm pretty sure this is a bug in SP8/Rev 80.
What other options do I have to "debug" any further?
By the way it makes no difference if I move the restriction from AT to CV1 or CV2, behavior is still the same (=wrong).
Hope you can help me since this is a major problem for my application!
Kind Regards,
Fabian

Answer 1

I cannot believe it. Rev. 91 and still the same Problem.
@SAP: Do you just don't care or are you not able to reproduce? I could provide small Delivery Unit with Schema, Table, AT and CVs as well as an analytic privilege.