The docstring for check_allocs in AllocCheck.jl warns, in part:
If you rely on allocation-free code for safety/correctness, it is not sufficient to verify check_allocs in test code and expect that the corresponding call in production will not allocate at runtime. For this case, you must use
@check_allocsinstead.
Does that mean check_allocs only checks 1 specified call signature while @check_allocs will statically check all runtime calls of the annotated method definition, or does @check_allocs actually have a superior allocation check than check_allocs somehow?