performance regression: Multiple allocations with "--check-bounds=no" on map after 1.9

[dpinol]

This always reports 1 allocation in julia <1.9

h(x) = (2,)
f(v) = @time Base.map(h, v)
f([2])
  0.000003 seconds (1 allocation: 64 bytes)
1-element Vector{Tuple{Int64}}:
 (2,)

But on julia 1.9 or master, when using --check-bounds=no it reports 6 allocations

h(x) = (2,)
f(v) = @time Base.map(h, v)
f([2])
  0.000020 seconds (6 allocations: 288 bytes)
1-element Vector{Tuple{Int64}}:
 (2,)

[oscardssmith]

This theoretically should be fixed by #50107. That said, see #48245 for why --checkbounds=no is probably a bad idea.