getFiltersForPolicy is a performance hotspot

[robfromboulder]

phileas-benchmark profiling shows that significant CPU time can be spent in the getFiltersForPolicy method (even with the recent addition of caching there). It might be worth considering a second level of caching where the result lists themselves don't have to be created each time?