The reason I added this is because I think it's the more common use case for testing, and prevents the caller from the temptation to guess what the actual format of the individual log entries is.  They are (somewhat arbitrary) arrays, and to do anything useful with them you need to index into them with hard-coded indexes (e.g. 0 == log level, 3 == message, etc.) that don't seem well known or appear to be documented anywhere.  This function doesn't *preclude* callers from composing the `count` themselves, but if we start establishing this function as the "best practice" pattern for our tests, it will help to hide the implementation details of the log entries themselves.  This seems desirable to me, but I won't put up a big fight if others feel strongly that the existence of this function actually causes some sort of problem.