Fix minor bug where the check whether to display SmartThreadPool stats was accidentally != null rather than == FireAndForgetMethod.SmartThreadPool

Due to another check this had no practical effect
minor: Change "memory churn" terminology in statistics to "heap allocation rate" since this is more generally meaningful