[GiNaC-list] Memory leak in dynallocate for relational

Hi, valgrind reports a memory leak caused by dynallocate<GiNaC::relational, const GiNaC::ex&, const GiNaC::ex&, GiNaC::relational::operators> (basic.h:336). I have attached a minimal example as well as the corresponding valgrind output I get. The executable was produced with g++ 5.4 -O0 and GiNaC 1.7.1. Repeated use of operators == or != for GiNaC::ex does indeed lead to a noticeable increase of memory usage in applications, whereas ex::is_equal does not have the same effect. Cheers, Thomas