Fix lambda date predicates

Meh - do what I want, not what I say. Of course the upper/lower
bounds have to be evaluated at the time of creating the lambda,
not when executing it. Error in that case: only the last date
parameter's values are used, for _all_ predicates.
Guard against non-existing txn split elements.
Collectively check today's fixes in a unit test.