Dynamic mvel constraints shouldn't be combined

Having a pattern like the following:

StockTick( company != $a.company, this before[5,8] $a.time || after[20,22] $a )

the PatternBuilder combines the 2 constraints in a single one. This is wrong because the 2nd constraint is dynamic (it uses custom operators) so it cannot be jit-optimized. Even worse the resulting combined constraint is flagged as non dynamic so the engine tries to jit it anyway, generating an excption during the jitting process.