MAYBE
1185.17/297.21	MAYBE
1185.17/297.21	
1185.17/297.21	We are left with following problem, upon which TcT provides the
1185.17/297.21	certificate MAYBE.
1185.17/297.21	
1185.17/297.21	Strict Trs:
1185.17/297.21	  { top(free(x)) -> top(check(new(x)))
1185.17/297.21	  , check(free(x)) -> free(check(x))
1185.17/297.21	  , check(new(x)) -> new(check(x))
1185.17/297.21	  , check(old(x)) -> old(x)
1185.17/297.21	  , check(old(x)) -> old(check(x))
1185.17/297.21	  , new(free(x)) -> free(new(x))
1185.17/297.21	  , new(serve()) -> free(serve())
1185.17/297.21	  , old(free(x)) -> free(old(x))
1185.17/297.21	  , old(serve()) -> free(serve()) }
1185.17/297.21	Obligation:
1185.17/297.21	  derivational complexity
1185.17/297.21	Answer:
1185.17/297.21	  MAYBE
1185.17/297.21	
1185.17/297.21	None of the processors succeeded.
1185.17/297.21	
1185.17/297.21	Details of failed attempt(s):
1185.17/297.21	-----------------------------
1185.17/297.21	1) 'Inspecting Problem... (timeout of 297 seconds)' failed due to
1185.17/297.21	   the following reason:
1185.17/297.21	   
1185.17/297.21	   Computation stopped due to timeout after 297.0 seconds.
1185.17/297.21	
1185.17/297.21	2) 'iteProgress (timeout of 297 seconds)' failed due to the
1185.17/297.21	   following reason:
1185.17/297.21	   
1185.17/297.21	   Computation stopped due to timeout after 297.0 seconds.
1185.17/297.21	
1185.17/297.21	3) 'Fastest (timeout of 60 seconds)' failed due to the following
1185.17/297.21	   reason:
1185.17/297.21	   
1185.17/297.21	   Computation stopped due to timeout after 60.0 seconds.
1185.17/297.21	
1185.17/297.21	4) 'bsearch-matrix (timeout of 297 seconds)' failed due to the
1185.17/297.21	   following reason:
1185.17/297.21	   
1185.17/297.21	   The input cannot be shown compatible
1185.17/297.21	
1185.17/297.21	
1185.17/297.21	Arrrr..
1185.17/297.22	EOF