Don't check for exact mem_used in DGM tests
Don't check for exact mem_used in DGM tests

The D>M tests assume that mem_used will be *exactly* the same after
the test as before. When using accurate memory tracking this is
unlikely to be the case. Seeing as these checks aren't the main thrust
of these two tests, remove them.

Change-Id: Ieaed79ffc0daeb99721a9b994ba6dccce8bab175
Reviewed-on: http://review.couchbase.org/42463
Reviewed-by: abhinav dangeti <d73ef2279de6577f7bf081737ee47554bbb7dc82@couchbase.com>
Tested-by: abhinav dangeti <d73ef2279de6577f7bf081737ee47554bbb7dc82@couchbase.com>

sriganes/ep-engine,jimwwalker/ep-engine,owendCB/ep-engine,jimwwalker/ep-engine,membase/ep-engine,couchbase/ep-engine,jimwwalker/ep-engine,hisundar/ep-engine,daverigby/kv_engine,daverigby/kv_engine,couchbase/ep-engine,membase/ep-engine,sriganes/ep-engine,daverigby/ep-engine,teligent-ru/ep-engine,teligent-ru/ep-engine,daverigby/kv_engine,daverigby/ep-engine,couchbase/ep-engine,jimwwalker/ep-engine,teligent-ru/ep-engine,owendCB/ep-engine,owendCB/ep-engine,teligent-ru/ep-engine,daverigby/ep-engine,couchbase/ep-engine,membase/ep-engine,membase/ep-engine,sriganes/ep-engine,owendCB/ep-engine,hisundar/ep-engine,daverigby/ep-engine,sriganes/ep-engine,hisundar/ep-engine,daverigby/kv_engine,hisundar/ep-engine